Optimization for Browser Rendering During Navigation

ABSTRACT

In various example embodiments, heavy document object model (DOM) elements in a heavy web page are removed directly from a DOM tree subsequent to a request being received to navigate to another web page but before the web browser actually navigates to that other web page. In one example embodiment, the heavy DOM elements are deleted from the previous page during an ‘onbeforeunload’ event using a scripting language such as Javascript, to ensure that the render of the next page starts faster.

PRIORITY

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/667,551, filed Oct. 29, 2019, entitled,“Optimization for Browser Rendering During Navigation”, which claimspriority to U.S. patent application Ser. No. 15/617,829, filed Jun. 8,2017, entitled, “Optimization for Browser Rendering During Navigation”,which claims priority to U.S. Provisional Application Ser. No.62/348,319, filed Jun. 10, 2016, entitled, “Rendering Optimizations”,the disclosures of which are incorporated by reference herein.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to web browsersoperating on computing devices. More particularly, embodiments of thepresent disclosure relate to optimizations of rendering of web browsers.

BACKGROUND

Web browsers operating on computing devices are software applicationsfor retrieving, presenting, and traversing information resources on theWorld Wide Web. These information resources are typically in the form ofa web page, image, video, or other piece of content that is readable bythe web browser. Users are able to navigate to and within web pages toobtain or view information.

Web browsers take content from the World Wide Web and render thatcontent so that it is visible on a display of the correspondingcomputing device on which the web browser is being run. Certain types ofweb pages, however, may introduce inefficiencies in the renderingprocess that cause themselves, or subsequently loaded web pages, torender slowly. Specifically, heavy web pages are subject to these typesof inefficiencies. Heavy web pages are web pages that include calls tocontent that is either slow to retrieve or slow to render, such as webpages with iFrames or calls to videos. What is needed are optimizationsto handle the inefficiencies introduced by heavy web pages on therendering process of web browsers.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present disclosure and cannot be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating a system including a web browserin accordance with an example embodiment.

FIG. 2 is a diagram illustrating the building of an example DOM by a webbrowser.

FIG. 3 is a diagram illustrating an example CSSOM.

FIG. 4 is a diagram illustrating the creation of a render tree.

FIG. 5 is a flow diagram illustrating a method of rendering of a webpage.

FIG. 6 is a navigation graph showing loading of a web page in a webbrowser in accordance with W3C standards.

FIG. 7 is a diagram depicting two timelines.

FIG. 8 is a navigation graph showing loading of a web page in a webbrowser where a delay occurs.

FIG. 9 is a flow diagram illustrating a method for optimizing renderingof a web page in accordance with an example embodiment.

FIG. 10 is an interaction diagram illustrating a method of optimizing aweb page in accordance with an example embodiment.

FIG. 11 is a block diagram illustrating an example of a softwarearchitecture that may be installed on a machine, according to someexample embodiments.

FIG. 12 illustrates a diagrammatic representation of a machine in theform of a computer system within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, according to an example embodiment.

The headings provided herein are merely for convenience and do notnecessarily affect the scope or meaning of the terms used.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

In various example embodiments, heavy document object model (DOM)elements in a heavy web page are removed directly from a DOM treesubsequent to a request being received to navigate to another web pagebut before the web browser actually navigates to that other web page. Inone example embodiment, the heavy DOM elements are deleted from theprevious page during an ‘onbeforeunload’ event using a scriptinglanguage such as Javascript, to ensure that the render of the next pagestarts faster.

FIG. 1 is a block diagram illustrating a system 110 including a webbrowser 112 in accordance with an example embodiment. The system 110represents one example system that can be used to implement theprocesses described herein. Specifically, in some example embodimentsembodiment, the one or more optimization techniques are implemented as aJavaScript or similar scripting language element, executed in a webbrowser 112 on a computing device 114. For ease of discussion, many ofthe aspects of the optimization techniques will be discussed in terms ofthis JavaScript or similar scripting language implementation.Nevertheless, these aspects could also be implemented on the otherexample systems and nothing in this disclosure should be interpreted aslimiting these aspects to the JavaScript or similar scripting languageimplementation.

The computing device 114 may be, for example, a desktop computer, laptopcomputer, tablet computer, smart phone, smart watch or any othercomputing device capable of displaying a graphical user interface via ascripting language and web browser combination. It should be noted,however, that in fact the further systems described later need not belimited to those computing devices capable of displaying a graphicaluser interface via a scripting language and web browser combination andcan, in fact, extend to any computing devices capable of displaying agraphical user interface.

The system 110 includes computing device 114 as well as a web server116. Web server 116 delivers a web page to the computing device 114 uponrequest. This request may either be explicit by the user of thecomputing device 114, such as navigating the web browser 112 to aspecific web address, or may be implicit or automatic. The web page may,for example, be in the form of Hypertext Markup Language (HTML) code orother markup language code, which may incorporate various calls and/orscripts through languages such as Cascade Style Sheets (CSS) andJavaScript.

An operating system 118 on the computing device 114 controlsinteractions between the web browser 112 and a user input device 120. Inother words, the operating system 120 can detect when a user interactswith the web browser 112 via input to the user input device 120 andtransmits such interactions to the web browser 112. Examples of userinput devices 120 include mice, keyboards, touchpads, touchscreens,microphones, and any other device capable of receiving user input. Theweb browser 112 can output rendered GUI elements on a display device 122of the computing device 114. In some example embodiments, the displaydevice 122 and the user input device 120 are the same device, such as inthe case of a touchscreen.

The web browser 112 contains its own user interface 124 (which maydisplay, for example, an address bar, back/forward button, bookmarkingmenu, etc.). A browser engine 126 marshals actions between the userinterface 124 and a rendering engine 128. The rendering engine 128 isresponsible for rendering content (e.g., web pages). The renderingengine 128 may contain one or more specialized parsers (e.g., HTMLparser, CSS parser) for this purpose.

A networking component 120 handles calls such as Hypertext TransferProtocol (HTTP) to and from the web server 116, using differentimplementations based on the platform, typically behind aplatform-independent interface. A user interface backend 122 handlesdrawing basic web page components such as buttons and windows. AJavaScript interpreter 124 is used to parse and execute JavaScript codefound in a web page parsed by the rendering engine 128. Finally, a datapersistence layer 126 allows the web browser 112 to save various typesof data locally, such as cookies.

In an example embodiment, specialized JavaScript code is provided to theJavaScript interpreter 124, either via a downloaded web page or bydirectly modifying one or more JavaScript libraries utilized by theJavaScript interpreter 124, which causes one or more optimizations tooccur on heavy elements in a web page at particular times.

Web browsers render a web page by first building a DOM, also known as aDOM tree, from the Hypertext Markup Language (HTML) or other codedefining the web page. The DOM/DOM tree is a data structure in whichelements of the web page are organized as nodes in a tree, withconnections between the nodes indicating an ordering for futurerendering. FIG. 2 is a diagram illustrating the building of an exampleDOM by a web browser. Here, the bytes 200 of incoming packets are parsedby a web parser to determine the characters 202 of the web page. Thecharacters 202 are then parsed by an HTML parser to a series of tokens204, each token representing a different element of the web page. A DOMparser then forms the tokens into nodes 206 and connects the nodes toform a DOM 208.

If Cascade Style Sheets (CSS) are used with the web page, then one ormore CSS documents related to the web page are parsed into a CSS ObjectModel (CSSOM). FIG. 3 is a diagram illustrating an example CSSOM 300.The CSSOM 300 includes one or more CSS elements 302A-302E, along withleaf nodes 304A-304E representing values for specific styles.

Then a render tree is created from the DOM and the CSSOM. FIG. 4 is adiagram illustrating the creation of a render tree 400. The render treeis created through a merging of the DOM 208 and the CSSOM 300. From therender tree 300, the visual objects of the web page are laid out andprinted on a display 402.

FIG. 5 is a flow diagram illustrating a method 500 of rendering of a webpage. The method 500 is divided into steps performed on the renderingengine 128 and steps performed elsewhere in the network. Here, therendering engine 128 requests a web page at operation 502. At operation504, a web page is obtained, and sent as a response in operation 506 tothe rendering engine 128. At operation 508, the rendering engine 128builds the DOM from the web page. Through this building process, it isdetermined that CSS files are referenced. At operation 510 these CSSdocuments are obtained and sent in a response to the rendering engine128 at operation 512. At operation 514 the CSSOM is built. At operation516, the rendering tree is built and at operation 518 the visualelements are laid out and painted on a display.

FIG. 6 is a navigation graph showing loading of a web page in a webbrowser in accordance with W3C standards. As can be seen, the unloading600 of a previously rendered web page is supposed to occur in parallelto the main request 602 and response 604 for the new web page. As such,the unloading 600 of the previously rendered web page should not affectthe rendering of the subsequently loaded web page. It was, however,discovered by the present inventor that there is, in practice, a delayintroduced in this process when heavy pages are rendered.

Specifically, FIG. 7 is a diagram depicting two timelines 700, 702. Thefirst timeline 700 depicts events occurring when rendering a web pagesubsequent to a light (i.e., non-heavy) web page, whereas the secondtimeline 702 depicts events occurring when rendering a web pagesubsequent to a heavy web page.

Notably, a delay 704 occurs in the second timeline between when thefirst byte of the new web page is received in the web browser and whenthe first rendering of the new web page begins.

This delay 704 is also depicted in the navigation graph of FIG. 8.

The ideal way to address this delay 704 is to design only light webpages, but this is practically difficult when product or other demandnecessitate that the web page contains heavy components, such as videolinks and iframes. Iframes are HTML elements that call other webcontent, such as advertisements, to render within a web page.

For example, a search results page may be presented in a web browser inresponse to a web search. When new advertisements are introduced onto asearch results page, even though these advertisements are lazily loadedafter a window load event, the time to first render of these pages isquite bad. This degradation in performance may even continue for allpages that had the search results page as a source page.

Furthermore, while the time to first render has degraded, the time tofirst byte does not degrade. Thus, after the web browser receives theresponse and before starting to render the page, this degradation can beobserved. The time between first byte and first render can be calculatedby subtracting the first byte time from the timestamp at the start ofthe markup. If this time can be called “browser think time”, then it isthis browser think time that is surprisingly high when navigating from aheavy web page. Specifically, it is the time between the domLoading anddomInteractive event where this degradation can be observed. domLoadingis triggered when the web browser is about to start parsing the firstreceived bytes of the HTML code, while domInteractive is triggered whenthe web browser has finished parsing enough HTML code and constructedthe DOM needed to start rendering the web page.

In an example embodiment, a solution is provided where heavy DOMelements are removed from a DOM tree before navigation to a new web page(i.e., when an onbeforeunload event is triggered). This may beperformed, for example, by introducing a JavaScript code into the webpage as follows:

window.addEventListener‘beforeunload’, function( ) { //Collect the heavyDOM elements var heavyElements =Array.prototype.slice.call(document.getElementsByTagName(‘iframe’));//Remove them from the DOM for (var i = 0, 1 = heavyElements.length; i<1; i++) { heavyElements [i]. parentNode . remove Child(heavyElements[i]); } });

The above script only addresses iframe elements but could be modifiedfor any heavy elements that can be contained in a web page.

FIG. 9 is a flow diagram illustrating a method 900 for optimizingrendering of a web page in accordance with an example embodiment. Atoperation 902, a first web page is rendered. The steps and substepsinvolved in rendering the first web page will not be described here asthe rendering of the first web page can actually be performed in anymanner, as long as at some point a DOM is created for the first webpage. In some example embodiments, the rendering of the first web pagemay have been performed in the same manner as will be described belowwith respect to the second web page, but in other example embodimentsthe first web page may simply be rendered in an ordinary fashion.

At operation 904, a prompt for unload event is detected. This prompt forunload event is typically an event thrown when a user attempts tonavigate from one web page to another web page in a web browser, eitherby the user explicitly selecting a link to the another web page or byvirtue of a web page or script automatically transferring the webbrowser to another web page. Nevertheless, in response to thisdetection, the remained of the method 900 is performed. Specifically, atoperation 906 a DOM for the first web page is traversed to locate one ormore heavy DOM elements in the DOM. At operation 908, the located one ormore heavy DOM elements are removed from the DOM. Notably, operations904-906 may be performed, in some example embodiments, using aJavaScript or other script associated with the first web page. Atoperation 910, the first web page is unloaded from the web browser. Atoperation 912, the second web page is received by the web browser. Atoperation 914, the second web page is rendered by the web browser. Insome example embodiments, the method 900 may be repeated by at thispoint looping back to operation 904, except this time performingoperations 906-810 for the second web page instead of the first, and infact this method 900 may continue to loop indefinitely for additionalweb pages.

FIG. 10 is an interaction diagram illustrating a method 1000 ofoptimizing a web page in accordance with an example embodiment. Themethod 1000 involves various components of a web browser, including userinterface 124, browser engine 126, rendering engine 128, and JavaScriptinterpreter 124. At operation 1002, a first web page is received by thebrowser engine 126. At operation 1004, the browser engine 126 passes thefirst web page to a rendering engine 128, which at operation 1006 actsto parse the web page. Discovery of JavaScript associated with the firstweb page during this parsing, the rendering engine 128 then sends thisJavaScript to the JavaScript interpreter 124 to interpret the JavaScriptat operation 108. The JavaScript interpreter then interprets thisJavaScript, which includes a script indicating actions to take inresponse to a prompt for unload event at operation 1010, and atoperation 1012 it instructs the browser engine as to these actions.

Also during the parsing, at operation 1014, the rendering engine 128forms a DOM from the first web page. At operation 1016, the renderingengine 128 renders the first web page in accordance with the DOM.

At operation 1018, the user interface 124 detects an action by the userthat causes navigation from the first web page to a second web page tooccur. This action may be, for example, the user selecting on a link tothe second web page, typing a uniform resource locator (URL) in anavigation bar of the web browser, or any other action that causes thenavigation to occur. At operation 1020, the user interface 124communicates this navigation to the browser engine 126. At operation1022, the browser engine 126 throws a prompt for unload event, causingthe actions from the JavaScript interpreter to be performed. Theseactions include, at operation 1024, scanning the DOM of the first webpage to locate any heavy DOM elements, and at operation 1026, removingthe heavy DOM elements from the DOM. At operation 1028, the browserengine 126 unloads the first web page.

At operation 1030, the second web page is received by the browser engine126. At operation 1032, the second web page is sent to the renderingengine 128, where at operation 1034 it is rendered.

In some example embodiments, applications other than a web browseritself may utilize one or more aspects of the above-described ideas. Forexample, a mobile application (“app”) operating on a mobile device mightalso parse DOM elements from web pages, despite not necessarily beingtermed a “web browser.” Additionally, in some example embodimentssimilar techniques can be applied outside of the DOM realm, with removalof heavy elements from other types of data structures used in rendering,either with a web browser embodiment or in a non-web browserenvironment.

It should be noted that removal of DOM elements via Javascript orsimilar techniques may actually be more efficient than leaving the webbrowser to perform the unload process. However, in some browserembodiments it may turn out to be costlier and in such cases it may bepreferable to forego such techniques and simply rely on the browser toperform the unloading without deletion of the heavy DOM elements fromthe DOM. In some example embodiments, this determination may bedynamically performed by analyzing one or more variables including, butnot limited to, the browser type, the hardware device on which thebrowser is operating (e.g, processing power, memory speed andavailability), current load on the hardware device on which the browseris operating, etc.

In other example embodiments, DOM elements may be classified under morecategories than just “heavy” and “light”. Specifically, intermediatelevels of heaviness may be specified and applied to certain types of DOMelements that are not quite as heavy as iframe elements or video links.The above-described dynamic determination of whether to remove suchelements may then factor in the level of heaviness in its determination.In some example embodiments, rather than a category assigned to elementsdenoting the heaviness a heaviness score may be assigned, which may makecalculations performed by the dynamic determination steps easier.

The use of the above techniques can be detected using, for example, abrowser extension that scans for heavy DOM elements in a web page beforeand after an unload event (e.g., ‘onbeforeunload’) is thrown. If theheavy elements in the DOM are missing subsequent to this unload event,it indicates usage of one or more of the above ideas.

Modules, Components, and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium) orhardware modules. A “hardware module” is a tangible unit capable ofperforming certain operations and may be configured or arranged in acertain physical manner In various example embodiments, one or morecomputer systems (e.g., a standalone computer system, a client computersystem, or a server computer system) or one or more hardware modules ofa computer system (e.g., a processor or a group of processors) may beconfigured by software (e.g., an application or application portion) asa hardware module that operates to perform certain operations asdescribed herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware module may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware modulemay include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwaremodules become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware module mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) may be driven by cost and time considerations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware module at one instance oftime and to constitute a different hardware module at a differentinstance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented modules. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented modules may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented modules may be distributed across a number ofgeographic locations.

Machine and Software Architecture

The modules, methods, applications and so forth described in conjunctionwith FIGS. 1-9 are implemented in some embodiments in the context of amachine and an associated software architecture. The sections belowdescribe representative software architecture(s) and machine (e.g.,hardware) architecture that are suitable for use with the disclosedembodiments.

Software architectures are used in conjunction with hardwarearchitectures to create devices and machines tailored to particularpurposes. For example, a particular hardware architecture coupled with aparticular software architecture will create a mobile device, such as amobile phone, tablet device, or so forth. A slightly different hardwareand software architecture may yield a smart device for use in the“internet of things.” While yet another combination produces a servercomputer for use within a cloud computing architecture. Not allcombinations of such software and hardware architectures are presentedhere as those of skill in the art can readily understand how toimplement the invention in different contexts from the disclosurecontained herein.

Software Architecture

FIG. 11 is a block diagram 1100 illustrating a representative softwarearchitecture 1102, which may be used in conjunction with varioushardware architectures herein described. FIG. 11 is merely anon-limiting example of a software architecture and it will beappreciated that many other architectures may be implemented tofacilitate the functionality described herein. The software architecture1102 may be executing on hardware such as machine 1200 of FIG. 12 thatincludes, among other things, processors 1210, memory 1230, and I/Ocomponents 1250. A representative hardware layer 1104 is illustrated andcan represent, for example, the machine 1200 of FIG. 12. Therepresentative hardware layer 1104 comprises one or more processingunits 1106 having associated executable instructions 1108. Executableinstructions 1108 represent the executable instructions of the softwarearchitecture 1102, including implementation of the methods, modules andso forth of FIGS. 1-9. Hardware layer 1104 also includes memory orstorage modules 1110, which also have executable instructions 1108.Hardware layer 1104 may also comprise other hardware as indicated by1112 which represents any other hardware of the hardware layer 1104,such as the other hardware illustrated as part of machine 1200.

In the example architecture of FIG. 11, the software 1102 may beconceptualized as a stack of layers where each layer provides particularfunctionality. For example, the software 1102 may include layers such asan operating system 1114, libraries 1116, frameworks/middleware 1118,applications 1120 and presentation layer 1122. Operationally, theapplications 1120 or other components within the layers may invokeapplication programming interface (API) calls 1124 through the softwarestack and receive a response, returned values, and so forth illustratedas messages 1126 in response to the API calls 1124. The layersillustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile or specialpurpose operating systems may not provide a frameworks/middleware layer1118, while others may provide such a layer. Other softwarearchitectures may include additional or different layers.

The operating system 1114 may manage hardware resources and providecommon services. The operating system 1114 may include, for example, akernel 1128, services 1130, and drivers 1132. The kernel 1128 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 1128 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1130 may provideother common services for the other software layers. The drivers 1132may be responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1132 may include display drivers,camera drivers, Bluetooth® drivers, flash memory drivers, serialcommunication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi®drivers, audio drivers, power management drivers, and so forth dependingon the hardware configuration.

The libraries 1116 may provide a common infrastructure that may beutilized by the applications 1120 and/or other components and/or layers.The libraries 1116 typically provide functionality that allows othersoftware modules to perform tasks in an easier fashion than to interfacedirectly with the underlying operating system 1114 functionality (e.g.,kernel 1128, services 1130, or drivers 1132). The libraries 1116 mayinclude system 1134 libraries (e.g., C standard library) that mayprovide functions such as memory allocation functions, stringmanipulation functions, mathematic functions, and the like. In addition,the libraries 1116 may include API libraries 1136 such as medialibraries (e.g., libraries to support presentation and manipulation ofvarious media format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG),graphics libraries (e.g., an OpenGL framework that may be used to render2D and 3D in a graphic content on a display), database libraries (e.g.,SQLite that may provide various relational database functions), weblibraries (e.g., WebKit that may provide web browsing functionality),and the like. The libraries 1116 may also include a wide variety ofother libraries 1138 to provide many other APIs to the applications 1120and other software components/modules.

The frameworks 1118 (also sometimes referred to as middleware) mayprovide a higher-level common infrastructure that may be utilized by theapplications 1120 or other software components/modules. For example, theframeworks 1118 may provide various graphic user interface (GUI)functions, high-level resource management, high-level location services,and so forth. The frameworks 1118 may provide a broad spectrum of otherAPIs that may be utilized by the applications 1120 and/or other softwarecomponents/modules, some of which may be specific to a particularoperating system or platform.

The applications 1120 includes built-in applications 1140 and/or thirdparty applications 1142. Examples of representative built-inapplications 1140 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. Third party applications 1142 may include anyof the built in applications as well as a broad assortment of otherapplications. In a specific example, the third party application 1142(e.g., an application developed using the Android™ or iOS™ softwaredevelopment kit (SDK) by an entity other than the vendor of theparticular platform) may be mobile software running on a mobileoperating system such as iOS™, Android™, Windows® Phone, or other mobileoperating systems. In this example, the third party application 1142 mayinvoke the API calls 1124 provided by the mobile operating system suchas operating system 1114 to facilitate functionality described herein.

The applications 1120 may utilize built in operating system functions(e.g., kernel 1128, services 1130 and/or drivers 1132), libraries (e.g.,system 1134, APIs 1136, and other libraries 1138), frameworks/middleware1118 to create user interfaces to interact with users of the system.Alternatively, or additionally, in some systems interactions with a usermay occur through a presentation layer, such as presentation layer 1144.In these systems, the application/module “logic” can be separated fromthe aspects of the application/module that interact with a user.

Some software architectures utilize virtual machines. In the example ofFIG. 11, this is illustrated by virtual machine 1148. A virtual machinecreates a software environment where applications/modules can execute asif they were executing on a hardware machine (such as the machine ofFIG. 12, for example). A virtual machine is hosted by a host operatingsystem (operating system 1114 in FIG. 12) and typically, although notalways, has a virtual machine monitor 1146, which manages the operationof the virtual machine as well as the interface with the host operatingsystem (i.e., operating system 1114). A software architecture executeswithin the virtual machine such as an operating system 1150, libraries1152, frameworks/middleware 1154, applications 1156 and/or presentationlayer 1158. These layers of software architecture executing within thevirtual machine 1148 can be the same as corresponding layers previouslydescribed or may be different.

Example Machine Architecture and Machine-Readable Medium

FIG. 12 is a block diagram illustrating components of a machine 1200,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 12 shows a diagrammatic representation of the machine1200 in the example form of a computer system, within which instructions1216 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1200 to perform any oneor more of the methodologies discussed herein may be executed. Forexample the instructions may cause the machine to execute the flowdiagram of FIG. 7. Additionally, or alternatively, the instructions mayimplement FIGS. 1-6, and so forth. The instructions transform thegeneral, non-programmed machine into a particular machine programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1200 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1200 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1200 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 1216, sequentially or otherwise, that specify actions to betaken by machine 1200. Further, while only a single machine 1200 isillustrated, the term “machine” shall also be taken to include acollection of machines 1200 that individually or jointly execute theinstructions 1216 to perform any one or more of the methodologiesdiscussed herein.

The machine 1200 may include processors 1210, memory 1230, and I/Ocomponents 1250, which may be configured to communicate with each othersuch as via a bus 1202. In an example embodiment, the processors 1210(e.g., a Central Processing Unit (CPU), a Reduced Instruction SetComputing (RISC) processor, a Complex Instruction Set Computing (CISC)processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(DSP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC), another processor, or anysuitable combination thereof) may include, for example, processor 1212and processor 1214 that may execute instructions 1216. The term“processor” is intended to include multi-core processor that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.12 shows multiple processors, the machine 1200 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core process), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory/storage 1230 may include a memory 1232, such as a mainmemory, or other memory storage, and a storage unit 1236, bothaccessible to the processors 1210 such as via the bus 1202. The storageunit 1236 and memory 1232 store the instructions 1216 embodying any oneor more of the methodologies or functions described herein. Theinstructions 1216 may also reside, completely or partially, within thememory 1232, within the storage unit 1236, within at least one of theprocessors 1210 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine1200. Accordingly, the memory 1232, the storage unit 1236, and thememory of processors 1210 are examples of machine-readable media.

As used herein, “machine-readable medium” means a device able to storeinstructions and data temporarily or permanently and may include, but isnot be limited to, random-access memory (RAM), read-only memory (ROM),buffer memory, flash memory, optical media, magnetic media, cachememory, other types of storage (e.g., Erasable Programmable Read-OnlyMemory (EEPROM)), or any suitable combination thereof. The term“machine-readable medium” should be taken to include a single medium ormultiple media (e.g., a centralized or distributed database, orassociated caches and servers) able to store instructions 1216. The term“machine-readable medium” shall also be taken to include any medium, orcombination of multiple media, that is capable of storing instructions(e.g., instructions 1216) for execution by a machine (e.g., machine1200), such that the instructions, when executed by one or moreprocessors of the machine 1200 (e.g., processors 1210), cause themachine 1200 to perform any one or more of the methodologies describedherein. Accordingly, a “machine-readable medium” refers to a singlestorage apparatus or device, as well as “cloud-based” storage systems orstorage networks that include multiple storage apparatus or devices. Theterm “machine-readable medium” excludes signals per se.

The I/O components 1250 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1250 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components1250 may include many other components that are not shown in FIG. 12.The I/O components 1250 are grouped according to functionality merelyfor simplifying the following discussion and the grouping is in no waylimiting. In various example embodiments, the I/O components 1250 mayinclude output components 1252 and input components 1254. The outputcomponents 1252 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1254 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1250 may includebiometric components 1256, motion components 1258, environmentalcomponents 1260, or position components 1262 among a wide array of othercomponents. For example, the biometric components 1256 may includecomponents to detect expressions (e g, hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1258 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1260 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1262 mayinclude location sensor components (e.g., a Global Position System (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1250 may include communication components 1264operable to couple the machine 1200 to a network 1280 or devices 1270via coupling 1282 and coupling 1272 respectively. For example, thecommunication components 1264 may include a network interface componentor other suitable device to interface with the network 1280. In furtherexamples, communication components 1264 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1270 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, the communication components 1264 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1264 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1264, such as, location via Internet Protocol (IP) geo-location,location via Wi-Fi® signal triangulation, location via detecting a NFCbeacon signal that may indicate a particular location, and so forth.

Transmission Medium

In various example embodiments, one or more portions of the network 1280may be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, the network 1280 or a portion of the network 1280may include a wireless or cellular network and the coupling 1282 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or other type of cellular orwireless coupling. In this example, the coupling 1282 may implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard setting organizations, other long rangeprotocols, or other data transfer technology.

The instructions 1216 may be transmitted or received over the network1280 using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components1264) and utilizing any one of a number of well-known transfer protocols(e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions1216 may be transmitted or received using a transmission medium via thecoupling 1272 (e.g., a peer-to-peer coupling) to devices 1270. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying instructions 1216 forexecution by the machine 1200, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Language

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the inventive subject matter may be referred to herein, individuallyor collectively, by the term “invention” merely for convenience andwithout intending to voluntarily limit the scope of this application toany single disclosure or inventive concept if more than one is, in fact,disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

1. A method comprising: rendering a web page, the rendering comprisingforming a document object model (DOM) from elements in the web page;scanning the DOM to locate one or more heavy elements of a plurality ofelements; and removing the located one or more heavy elements of theplurality of elements from the DOM.
 2. The method as described in claim1, wherein the located one or more heavy elements includes an iFrameelement.
 3. The method as described in claim 2, wherein the iFrameelement includes a call to an advertisement.
 4. The method as describedin claim 1, wherein the located one or more heavy elements includes avideo link.
 5. The method as described in claim 1, wherein the removingthe located one or more heavy elements of the plurality of elements fromthe DOM is performed before rendering a second web page.
 6. The methodof claim 1, wherein the rendering the web page and the removing thelocated one or more heavy elements of the plurality of elements from theDOM is performed by a web browser.
 7. A method comprising: rendering afirst web page; receiving user input to navigate to a second web page;in response to the user input, removing one or more heavy elements froma data structure used to render the first web page; subsequent toremoving the one or more heavy elements from the data structure,unloading the first web page; and rendering a second web page.
 8. Themethod as described in claim 7, wherein the removing the one or moreheavy elements is performed before rendering the second web page.
 9. Themethod as described in claim 7, wherein the rendering the first webpage, removing the one or more heavy elements, unloading the first webpage, and rendering the second web page is performed by a web browser.10. The method as described in claim 7, wherein the rendering the firstweb page, removing the one or more heavy elements, unloading the firstweb page, and rendering the second web page is performed by anapplication other than a web browser.
 11. The method as described inclaim 7, wherein the one or more heavy elements includes an iframeelement.
 12. The method as described in claim 7, wherein the one or moreheavy elements includes a video link.
 13. The method as described inclaim 7, wherein the removing the one or more heavy elements isperformed after detecting the user input.
 14. The method as described inclaim 7, wherein the removing the one or more heavy elements includesnot removing other elements of a plurality of elements of the datastructure.
 15. The method as described in claim 7, wherein the datastructure comprises a document object model (DOM).
 16. A computingdevice comprising: at least a memory and a processor to performoperations comprising: rendering a first web page; receiving user inputto navigate to a second web page; in response to the user input,removing one or more heavy elements from a data structure used to renderthe first web page; subsequent to removing the one or more heavyelements from the data structure, unloading the first web page; andrendering a second web page.
 17. The computing device as described inclaim 16, wherein the removing the one or more heavy elements isperformed before rendering the second web page.
 18. The computing deviceas described in claim 16, wherein the rendering the first web page,removing the one or more heavy elements, unloading the first web page,and rendering the second web page is performed by a web browser.
 19. Thecomputing device as described in claim 16, wherein the rendering thefirst web page, removing the one or more heavy elements, unloading thefirst web page, and rendering the second web page is performed by anapplication other than a web browser.
 20. The computing device asdescribed in claim 16, wherein the one or more heavy elements includesat least one of an iframe element or a video link.